-
-
Notifications
You must be signed in to change notification settings - Fork 52
Experimental async/await support #112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Time Change: -843ms (9%) ✅ Total Time: 9,170.5ms
ℹ️ View Unchanged
|
Do I understand correctly that after this is merged we'll require our users to use dev toolchains and to compile with experimental concurrency enabled? |
Also, could we link with Swift runtime parts that are already included in the toolchain/SDK? Is a copy of it and LLVM stuff in our codebase required for this to work? |
Yes, so I'm planning to merge this to
|
Fair enough. I'm only worried that contents of these headers can change in a breaking way, especially given that concurrency stuff isn't ABI-stable yet, and maybe there's a better way to track them. A submodule is probably not practical due to the size of repositories that have these headers, so I don't have a better alternative to propose... Maybe some kind of scripts that pull latest versions of these headers automatically? 🤔 |
Yes, so I wrote a shell script to fetch headers from https://github.com/swiftwasm/JavaScriptKit/blob/366d74e82e3aa40d604ac843743bb59b9412243b/Sources/_CJavaScriptEventLoop/README |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems legit then 👍
Current Issues
-enable-experimental-concurrency
. If we remove it from Package.swift, users have to pass it from command line.